History

Navigation bar > > Reports > History

The History section provides a complete record of all report generation and delivery activities.

It allows administrators to monitor system performance, verify successful deliveries, and identify issues during report generation or account tests*.

*Note: user accessibility to these functions is managed by the type of user permissions.

Each record in the History log contains detailed information about report execution and delivery. The system automatically logs the following events:

Element

Description

 
Generation start and end times Schedule name.  
Template Report template (must be owned or shared).  
Account Account used for delivery.  
Delivery status

It includes:

  • Generated successfully,

  • Delivered successfully,

  • Generation error,

  • Delivery error (with up to three retry attempts recorded).

  

Logs are created for both report generation and delivery and for account test operations.

Any error or warning—such as failed connections, invalid credentials, or interrupted transfers—is captured and clearly marked.

The log list can be filtered to make navigation easier. Users can refine results using one or more of the following filters:

  • Report name or template,

  • Account,

  • Time range,

  • Error type or status.

Filtered results can be exported for audit or diagnostic purposes in standard formats (for example CSV or PDF). Exported logs retain all relevant timestamps and metadata for traceability.

The system ensures that access to log information remains both transparent and secure.

Logs are organized and displayed according to the operation they relate to, and several safeguards are applied to protect sensitive data and ensure traceability.

  • Access control: Logs for account test operations are visible within the Account section, while logs for generated reports are available in the Report History section.

  • Data protection: Sensitive information such as passwords, tokens, or encryption keys is never displayed or stored in logs.

  • Retention policy: Log retention follows the system’s storage capacity and compliance requirements, ensuring data is preserved only as long as necessary.

  • Error traceability: Each log entry indicates the exact stage at which an error occurred—whether during report generation or delivery—and includes details on any retry attempts made.

These measures guarantee that administrators can safely monitor the reporting system while maintaining confidentiality and data integrity.